feat: implement authentication support #346
Draft
+526
−36
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
frezbo
reviewed
Dec 29, 2025
smira
force-pushed
the
feat/authentication-support
branch
from
26120a2 to
f780b73
Compare
smira
force-pushed
the
feat/authentication-support
branch
3 times, most recently
from
20641d3 to
a899895
Compare
This feature is Enterprise only (requires BUSL). Any access to the schematic requires the user to be authenticated before access. Moreover, any schematic stores the owner in the schematic, so each schematic becomes private (owned by the user which created it). Authentication is configured using a set of usernames and keys associates with each user (API key). Signed-off-by: Andrey Smirnov <[email protected]>
smira
force-pushed
the
feat/authentication-support
branch
from
a899895 to
fee7bab
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This feature is Enterprise only (requires BUSL).
Any access to the schematic requires the user to be authenticated before access.
Moreover, any schematic stores the owner in the schematic, so each schematic becomes private (owned by the user which created it).
Authentication is configured using a set of usernames and keys associates with each user (API key).